-
-
Notifications
You must be signed in to change notification settings - Fork 26.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Catch "No tests found" during CI #2387
Conversation
Related to this, I've opened a PR in jest in order to add a CLI arg ( |
Thanks! |
@gaearon sorry for not giving an immediate feedback on this, but probably all past appveyor CI "kitchensink" builds skipped the unit tests. This PR was indeed to see if that could be catched, but I managed to cause a segmentation fault in npm (?!?). Fact is, we have still no unit test coverage on windows 😞.. |
...aaand it seems like you figured it out 😛 |
Yea, I just reverted for now 😄 |
* master: Add WebStorm >2017 launchEditor Support (facebook#2414) docs: update `jest-enzyme` section (facebook#2392) Fix detection of parent directory in ModuleScopePlugin (facebook#2405) Added cache clear to e2e scripts (facebook#2400) Fix kill command in e2e-kitchensink.sh cleanup (facebook#2397) Revert "Catch "No tests found" during CI" (facebook#2390) Fix wrong path expansion in end-to-end test (facebook#2388) Suggest just "yarn build" (facebook#2385) Catch "No tests found" during CI (facebook#2387) Publish Add changelog for 1.0.7 (facebook#2384) Update webpack to 2.6.1 (facebook#2383) Consistently set environment variables (facebook#2382) Disable comparisons feature in uglify compression in production (facebook#2379) Removed the overriding of reduce_vars to false since webpack v2.6.0 included the fixed for Uglify bug (facebook#2351)
* Revert "Fix wrong path expansion in end-to-end test (facebook#2388)" This reverts commit 2aafaad. * Revert "Suggest just "yarn build" (facebook#2385)" This reverts commit 70bf125. * Revert "Catch "No tests found" during CI (facebook#2387)" This reverts commit 5317b3f.
As noted in #2285, appveyor tests are failing.
This PR is intended as a patch to cover this case, while the kitchensink CI tests are fixed.